Join feature restoration to online meeting

ABSTRACT

Features to join an online meeting are crucial to successfully conducting the online meeting. Accordingly, embodiments are directed to restoration of such features to an online meeting generated without a join feature or an online meeting in which the join feature was never added or accidentally removed. A client application may be configured to receive an online meeting, detect an absence of metadata associated with a join feature upon analysis of the online meeting, parse a body of the online meeting to detect a collection of one or more URLs, verify each of the URLs with a HTTP get operation, and in response to a determination that a URL comprises an online meeting identifier, recreate the metadata with the URL to generate the join feature. Once restored, the join feature may be presented within an invitation for the online meeting.

CROSS-REFERENCE TO RELATED APPLICATION

This application claims benefit under 35 U.S.C. § 119(e) of U.S.Provisional Application No. 62/380,479 filed on Aug. 28, 2016. The U.S.Provisional Application is herein incorporated by reference in itsentirety.

BACKGROUND

Features to join an online meeting such as a join link are crucial tosuccessfully conducting the online meeting. However, for a variety ofreasons, an online meeting may be generated without a join link or thejoin link may be accidently removed from the online meeting. Forexample, an invitee may be associated with an organization that is notfederated with an organization of the organizer. As such, metadata ofthe online meeting that includes features to join the meeting may beerased or dropped when delivering the online meeting to the invitee. Anorganizer may also copy and paste the online meeting to another meetinginvitation and the join features may fail to be added to the othermeeting invitation. As a result, restoring join features to an onlinemeeting may be important to successfully conducting the meeting.

SUMMARY

This summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This summary is not intended to exclusively identify keyfeatures or essential features of the claimed subject matter, nor is itintended as an aid in determining the scope of the claimed subjectmatter.

Embodiments are directed to restoration of a join feature to an onlinemeeting. For example, a productivity service may receive an onlinemeeting, detect an absence of a metadata associated with the joinfeature upon analysis of the online meeting, parse a body of the onlinemeeting to detect a collection of URLs, verify each URL of thecollection with a HTTP get operation, in response to a determinationthat a URL from the collection comprises an online meeting identifierrecreate the metadata of the online meeting with the URL to generate thejoin feature, and update the online meeting with the metadata such thatthe join feature is able to be restored upon execution of one or moreoperations. Some of these actions may be performed similarly by aclient, such as an application of the productivity service executing ona client device.

These and other features and advantages will be apparent from a readingof the following detailed description and a review of the associateddrawings. It is to be understood that both the foregoing generaldescription and the following detailed description are explanatory anddo not restrict aspects as claimed.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1A-C include display diagrams illustrating example networkenvironments where restoration of a join feature to an online meetingmay be implemented.

FIG. 2 includes a display diagram illustrating an example scheme torestore a join feature to an online meeting;

FIG. 3 includes a display diagram illustrating an example onlinemeeting;

FIG. 4 includes a display diagram illustrating an example userexperience rendering a join feature;

FIG. 5 is an example networked environment, arranged in accordance withat least some embodiments described herein;

FIG. 6 illustrates a general purpose computing device, which may beconfigured to restore a join feature to an online meeting, arranged inaccordance with at least some embodiments described herein;

FIG. 7 illustrates a logic flow diagram for an example server-sideprocess to restore a join feature to an online meeting; and

FIG. 8 illustrates a logic flow diagram for an example client-sideprocess to restore a join feature to an online meeting, arranged inaccordance with at least some embodiments described herein.

DETAILED DESCRIPTION

As briefly described above, embodiments are directed to restoration of ajoin feature to an online meeting. The join feature may be a join linkand/or a join button configured to execute an operation to join theonline meeting. A productivity service or a client applicationassociated with the productivity service may initiate operations torestore the join feature upon receiving an online meeting. For example,an online meeting may be analyzed to detect an absence of a metadataassociated with the join feature. In response, a body of the onlinemeeting may be parsed to detect a collection of URLs, each URL of thecollection may be verified with a HTTP get operation, and in response toa determination that a URL from the collection comprises an onlinemeeting identifier, the metadata of the online meeting may be createdwith the URL to generate the join feature.

In the following detailed description, references are made to theaccompanying drawings that form a part hereof, and in which are shown byway of illustrations, specific embodiments, or examples. These aspectsmay be combined, other aspects may be utilized, and structural changesmay be made without departing from the spirit or scope of the presentdisclosure. The following detailed description is therefore not to betaken in a limiting sense, and the scope of the present invention isdefined by the appended claims and their equivalents.

While some embodiments will be described in the general context ofprogram modules that execute in conjunction with an application programthat runs on an operating system on a personal computer, those skilledin the art will recognize that aspects may also be implemented incombination with other program modules.

Generally, program modules include routines, programs, components, datastructures, and other types of structures that perform particular tasksor implement particular abstract data types. Moreover, those skilled inthe art will appreciate that embodiments may be practiced with othercomputer system configurations, including hand-held devices,multiprocessor systems, microprocessor-based or programmable consumerelectronics, minicomputers, mainframe computers, and comparablecomputing devices. Embodiments may also be practiced in distributedcomputing environments where tasks are performed by remote processingdevices that are linked through a communications network. In adistributed computing environment, program modules may be located inboth local and remote memory storage devices.

Some embodiments may be implemented as a computer-implemented process(method), a computing system, or as an article of manufacture, such as acomputer program product or computer readable media. The computerprogram product may be a computer storage medium readable by a computersystem and encoding a computer program that comprises instructions forcausing a computer or computing system to perform example process(es).The computer-readable storage medium is a computer-readable memorydevice. The computer-readable storage medium can for example beimplemented via one or more of a volatile computer memory, anon-volatile memory, a hard drive, a flash drive, a floppy disk, or acompact disk, and comparable hardware media.

Throughout this specification, the term “platform” may be a combinationof software and hardware components to restore a join feature to anonline meeting. Examples of platforms include, but are not limited to, ahosted service executed over a plurality of servers, an applicationexecuted on a single computing device, and comparable systems. The term“server” generally refers to a computing device executing one or moresoftware programs typically in a networked environment. However, aserver may also be implemented as a virtual server (software programs)executed on one or more computing devices viewed as a server on thenetwork. More detail on these technologies and example operations isprovided below.

FIGS. 1A-C include display diagrams illustrating example networkenvironments where restoration of a join feature to an online meetingmay be implemented. As illustrated in diagrams 100A-C, an example systemmay include a datacenter 112 hosting a cloud-based productivity service114 configured to enable users to create, edit, and/or share contentamong multiple devices and across a variety of platforms. The datacenter112 may include one or more processing servers 116 configured to executethe productivity service 114, among other components. The datacenter 112may also include one or more storage servers 120 configured to manageone or more data stores comprising data associated with the productivityservice 114. As described herein, the productivity service 114 may beimplemented as software, hardware, or combinations thereof.

In some embodiments, the productivity service 114 may be configured tointeroperate with various applications. For example, as illustrated inthe diagrams 100A-C, a user 104 may execute a thin (e.g., a web browser)or a thick (e.g., a locally installed client application) version of anapplication 106 through a device 102 with which the productivity service114 may be configured to integrate and interoperate with over one ormore networks, such as network 110. The application 106 may be anapplication hosted by the productivity service 114. The application 106may be configured to store information, such as an online meeting, inlocal storage 108 of the device, or provide the information to theproductivity service 114 for remote storage at the storage servers 120.The application 106 may be a communication application, a calendarapplication, a word-processing application, a notebook application,and/or a spreadsheet application among other examples. The device 102may include a desktop computer, a laptop computer, a tablet computer, avehicle mount computer, a smart phone, or a wearable computing device,among other similar devices. A communication interface may facilitatecommunication between the productivity service 114 and the application106 over the network 110.

In one embodiment, as illustrated in diagram 100A, at least one of theprocessing servers 116 may be operable to execute a communication module118 of the productivity service 114, where the communication module 118may be integrated with the productivity service 114 to restore a joinfeature to an online meeting. In another embodiment, as illustrated indiagram 100B, the application 106 may be operable to execute thecommunication module 118, where the communication module 118 may beintegrated with the application 106. In a further embodiment, asillustrated in diagram 100C, the communication module 118 may be aseparate module associated with and/or executed by one or moreprocessing servers 124 of a third party service 122 configured to servemultiple applications, such as the application 106 of the productivityservice 114.

In an example embodiment, an online meeting may be generated by ameeting organizer through the application 106. Alternatively, the onlinemeeting may be provided from the third party service 122, such as acalendar provider. The online meeting may be newly generated or theonline meeting may be already existent but recently edited. Thecommunication module 118 may be configured to receive the online meetingand analyze the online meeting to detect an absence of metadata. Theabsent metadata may include information to generate and/or insert a joinfeature, such as a join link, into the online meeting.

In response to detecting the absence of the metadata, the communicationmodule 118 may parse a body of the online meeting to detect a collectionof one or more URLs. The communication module 118 may be configured toemploy pattern matching to identify the collection of URLs. Each URL ofthe collection may be verified with a HTTP get operation to determinewhether any of the URLs comprise an online meeting identifier.

In response to a determination that single URL comprises an onlinemeeting identifier, the communication module 118 may be configured torecreate the metadata with the URL to generate a join feature. Themetadata may also be recreated in response to a determination thatmultiple URLs have a same online meeting identifier. The join featuremay be a join link and/or a join button configured to execute anoperation to join the online meeting. The communication module 118 maythen be configured to update the online meeting with the metadata suchthat the join feature is able to be restored in response to receiving anotification of an invitee's intent to join the online meeting such thatthe invitee is enabled to join the online meeting using the joinfeature. Alternatively, the communication module 118 may be configuredto immediately insert the join feature into the online meeting upon itsgeneration. The join feature may be provided for display through a userexperience of the application 106. For example, the join feature may bepresented within an invitation for the online meeting.

In response to a determination, the no URLs comprise a meetingidentifier, the recreation of the metadata is foregone. Similarly, inresponse to a determination that multiple URLs comprise online meetingidentifiers and those online meeting identifiers are distinct, therecreation of the metadata is foregone

Some of the actions and/or processes described herein have beenillustrated from the perspective of a server (for example, theprocessing servers 116 configured to execute the productivity service114), however similar actions may be performed similarly by a client(for example, the application 106), among other entities.

As previously discussed features to join an online meeting are crucialto successfully conducting the online meeting, however an online meetingmay be generated without join link metadata or the join link metadatamay fail to be added or may be accidentally removed. Embodiments aredirected to restoration of a join feature to ensure the meeting issuccessfully conducted. The restoration of the join feature may improveperformance, increase reliability, and reduce processing and networkbandwidth usage by employing pattern matching and verificationtechniques to detect the URL. Additionally, the restoration of the joinfeature may improve user interaction by enabling a user to easily joinan online meeting.

Embodiments, as described herein, address a need that arises from verylarge scale of operations created by software-based services that cannotbe managed by humans. The actions/operations described herein are not amere use of a computer, but address results of a system that is a directconsequence of software used as a service offered in conjunction withuser communication through productivity services hosted across a varietyof platforms and devices.

FIG. 2 includes a display diagram illustrating an example scheme torestore a join feature to an online meeting. As shown in a diagram 200,a productivity service 202, executed by one or more processing servers204, may be configured to generate and restore a join feature to anonline meeting. The productivity service 202 may be configured toreceive and analyze an online meeting 206. During the analysis, anabsence of metadata associated with a join feature of the online meetingmay be detected.

In response to detecting the absence of the metadata, the productivityservice 202 may be configured to parse a body of the online meeting 206to detect a collection of URLs 204. The body of the online meeting 206may be formatted in hypertext markup language (HTML). A collection ofthe URLs 204 that start with http:// and https:// may be detected byemploying pattern matching within the body of the online meeting 206.Each URL of the collection of URLs 204 may be verified with a HTTP getoperation (and/or a HTTPs get operation). Verification reveal whether ornot each URL has an online meeting identifier. A number of URLs in thecollection of the URLs 204 may be limited to prevent processing andverification of a large number of the URLs to save computationalresources and prevent unnecessary processing of wrong candidate URLs.For example, prior to verification, duplicate URLs may be removed fromthe collection of URLs 204. For further example, after verification, ifno URL comprises an online meeting identifier, the restoration of thejoin feature may be blocked. Similarly, if multiple URLs in the samebody of the online meeting 206 body comprise online meeting identifiersthat are distinct from one another, the restoration of the join featuremay be blocked because there may be no objective way to determine whichone of the multiple URLs is the intended link to the online meeting. Ifexactly one URL comprises an online meeting identifier, such as URL 208,then the productivity service 202 may assume URL 208 is the valid linkfor the online meeting. The productivity service 202 may automaticallyrecreate the metadata 210 with the URL 208 to generate the join feature212 and insert the metadata 210 with the URL 208 into the online meeting206.

The productivity service 202 may be configured to execute operations torestore the join feature 212 upon receiving a notification of a meetinginvitee's intent to join the online meeting 206. The productivityservice 202 may restore the join feature 212 to allow the invitee tojoin the online meeting 206 by using the join feature 212. Theproductivity service 202 may also be configured to execute operations torestore the join feature 212 when the online meeting 206 is generated.The join feature 212 may be provided for display through an invitationto the online meeting 206.

The actions and/or processes described herein have been illustrated fromthe perspective of a server (for example, the processing servers 204configured to execute the productivity service 202). However,alternative embodiments are directed toward a client application beingconfigured to restore the join feature for an online meeting (forexample, an application associated with the productivity service 202that is being executed by a client device). Some of the actions and/orprocesses may be performed similarly by the client application

FIG. 3 includes a display diagram illustrating an example onlinemeeting. A productivity service may be configured to restore a joinfeature to an online meeting. Upon receipt, an online meeting may beanalyzed to detect an absence of metadata associated with a join featureof the online meeting. In response to detecting the absence of themetadata, a body of the online meeting may be parsed to detect acollection of URLs. Upon determination that one of the URLs from thecollection may include a destination that may be used to join the onlinemeeting (that is, the URL comprised an online meeting identifier). Themetadata may be recreated with the URL to generate the join feature.

As shown in a diagram 300, a client interface (or a client application)associated with the productivity service, such as a communicationapplication comprising a scheduling component 302, may access themetadata to generate a join feature 308. In response to a user selectionof the online meeting 304 through the scheduling component 302, the joinfeature 308 may be displayed in a menu 306 among other featuresassociated with the online meeting 304. The other features may includeto communicate with attendees of the online meeting and cancel theonline meeting, for example. Additionally, and/or alternatively, thejoin feature 308 may be presented within an invitation to the onlinemeeting, as described in more detail in FIG. 4.

FIG. 4 includes a display diagram illustrating an example userexperience rendering a join feature. A productivity service may beconfigured to restore a join feature to an online meeting. Upon receipt,an online meeting may be analyzed to detect an absence of metadataassociated with a join feature of the online meeting. In response todetecting the absence of the metadata, a body of the online meeting maybe parsed to detect a collection of URLs. Upon determination that one ofthe URLs from the collection may include a destination that may be usedto join the online meeting (that is, the URL comprised an online meetingidentifier). The metadata may be recreated with the URL to generate thejoin feature.

As shown in a diagram 400, a client interface (or a client application)associated with the productivity service, such as a communicationapplication, may access the recreated metadata to restore a join feature404. The productivity service may also provide a user experience topresent the join feature 404 within an invitation to the online meeting402. Additional join features 406, such as options to join the meetingby phone, may also be provided within the invitation to the onlinemeeting 402.

The examples provided in FIG. 1 through FIG. 4 are illustrated withspecific systems, services, applications, modules, and user experiences.Embodiments are not limited to environments according to these examples.Restoration of a join feature to an online meeting may be implemented inenvironments employing fewer or additional systems, services,applications, modules, and user experiences. Furthermore, the examplesystems, services, applications, modules, and user experiences shown inFIG. 1 through FIG. 4 may be implemented in a similar manner with othervalues using the principles described herein.

FIG. 5 is an example networked environment, arranged in accordance withat least some embodiments described herein. In addition to locallyinstalled applications (for example, application 106), a communicationmodule may also be employed in conjunction with hosted applications andservices (for example, a productivity service 114) that may beimplemented via software executed over one or more servers 506 orindividual server 508, as illustrated in diagram 500. A hosted serviceor application may communicate with client applications on individualcomputing devices such as a handheld computer 501, a desktop computer502, a laptop computer 503, a smart phone 504, a tablet computer (orslate), 505 (‘client devices’) through network(s) 510 and control a userinterface presented to users.

Client devices 501-505 are used to access the functionality provided bythe hosted service or application. One or more of the servers 506 orserver 508 may be used to provide a variety of services as discussedabove. Relevant data may be stored in one or more data stores (e.g. datastore 514), which may be managed by any one of the servers 506 or bydatabase server 512.

Network(s) 510 may comprise any topology of servers, clients, Internetservice providers, and communication media. A system according toembodiments may have a static or dynamic topology. Network(s) 510 mayinclude a secure network such as an enterprise network, an unsecurenetwork such as a wireless open network, or the Internet. Network(s) 510may also coordinate communication over other networks such as PSTN orcellular networks. Network(s) 510 provides communication between thenodes described herein. By way of example, and not limitation,network(s) 510 may include wireless media such as acoustic, RF, infraredand other wireless media.

Many other configurations of computing devices, applications, engines,and modules may be employed to restore a join feature to an onlinemeeting. Furthermore, the networked environments discussed in FIG. 5 arefor illustration purposes only. Embodiments are not limited to theexample services, applications, engines, modules or processes.

FIG. 6 illustrates a general purpose computing device, which may beconfigured to restore a join feature to an online meeting, arranged inaccordance with at least some embodiments described herein.

For example, computing device 600 may be used as a server, desktopcomputer, portable computer, smart phone, special purpose computer, orsimilar device. In an example basic configuration 602, the computingdevice 600 may include one or more processors 604 and a system memory606. A memory bus 608 may be used for communicating between theprocessor 604 and the system memory 606. The basic configuration 602 isillustrated in FIG. 6 by those components within the inner dashed line.

Depending on the desired configuration, the processor 604 may be of anytype, including but not limited to a microprocessor (μP), amicrocontroller (μC), a digital signal processor (DSP), or anycombination thereof. The processor 604 may include one more levels ofcaching, such as a level cache memory 612, one or more processor cores614, and registers 616. The example processor cores 614 may (each)include an arithmetic logic unit (ALU), a floating point unit (FPU), adigital signal processing core (DSP Core), or any combination thereof.An example memory controller 618 may also be used with the processor604, or in some implementations the memory controller 618 may be aninternal part of the processor 604.

Depending on the desired configuration, the system memory 606 may be ofany type including but not limited to volatile memory (such as RAM),non-volatile memory (such as ROM, flash memory, etc.) or any combinationthereof. The system memory 606 may include an operating system 620, aproductivity service 622, and program data 624. The productivity service622 may include a communication module 626, which may be an integratedmodule of the productivity service 622. In other embodiments, thecommunication module 626 may be an integrated module of a locallyinstalled application of the productivity service 622 or thecommunication module 626 may be a separate module associated with athird party service configured to serve multiple applications of theproductivity service 622. The communication module 622 may be configuredto restore a join feature to an online meeting. For example, thecommunication module 622 may be configured to receive an online meeting,detect an absence of a metadata upon analysis of the online data, parsea body of the online meeting to detect a URL, verify the URL with a HTTPget operation, recreate the metadata with the URL, and update the onlinemeeting with the metadata. The program data 624 may include, among otherdata, process data 628 such as the metadata and URLs as describedherein.

The computing device 600 may have additional features or functionality,and additional interfaces to facilitate communications between the basicconfiguration 602 and any desired devices and interfaces. For example, abus/interface controller 630 may be used to facilitate communicationsbetween the basic configuration 602 and one or more data storage devices632 via a storage interface bus 634. The data storage devices 632 may beone or more removable storage devices 636, one or more non-removablestorage devices 638, or a combination thereof. Examples of the removablestorage and the non-removable storage devices include magnetic diskdevices such as flexible disk drives and hard-disk drives (HDDs),optical disk drives such as compact disk (CD) drives or digitalversatile disk (DVD) drives, solid state drives (SSD), and tape drivesto name a few. Example computer storage media may include volatile andnonvolatile, removable and non-removable media implemented in any methodor technology for storage of information, such as computer readableinstructions, data structures, program modules, or other data.

The system memory 606, the removable storage devices 636 and thenon-removable storage devices 638 are examples of computer storagemedia. Computer storage media includes, but is not limited to, RAM, ROM,EEPROM, flash memory or other memory technology, CD-ROM, digitalversatile disks (DVDs), solid state drives, or other optical storage,magnetic cassettes, magnetic tape, magnetic disk storage or othermagnetic storage devices, or any other medium which may be used to storethe desired information and which may be accessed by the computingdevice 600. Any such computer storage media may be part of the computingdevice 600.

The computing device 600 may also include an interface bus 640 forfacilitating communication from various interface devices (for example,one or more output devices 642, one or more peripheral interfaces 644,and one or more communication devices 646) to the basic configuration602 via the bus/interface controller 630. Some of the example outputdevices 642 include a graphics processing unit 648 and an audioprocessing unit 650, which may be configured to communicate to variousexternal devices such as a display or speakers via one or more A/V ports652. One or more example peripheral interfaces 644 may include a serialinterface controller 654 or a parallel interface controller 656, whichmay be configured to communicate with external devices such as inputdevices (for example, keyboard, mouse, pen, voice input device, touchinput device, etc.) or other peripheral devices (for example, printer,scanner, etc.) via one or more I/O ports 658. An example communicationdevice 646 includes a network controller 660, which may be arranged tofacilitate communications with one or more other computing devices 662over a network communication link via one or more communication ports664. The one or more other computing devices 662 may include servers,computing devices, and comparable devices.

The network communication link may be one example of a communicationmedia. Communication media may typically be embodied by computerreadable instructions, data structures, program modules, or other datain a modulated data signal, such as a carrier wave or other transportmechanism, and may include any information delivery media. A “modulateddata signal” may be a signal that has one or more of its characteristicsset or changed in such a manner as to encode information in the signal.By way of example, and not limitation, communication media may includewired media such as a wired network or direct-wired connection, andwireless media such as acoustic, radio frequency (RF), microwave,infrared (IR) and other wireless media. The term computer readable mediaas used herein may include both storage media and communication media.

The computing device 600 may be implemented as a part of a generalpurpose or specialized server, mainframe, or similar computer thatincludes any of the above functions. The computing device 600 may alsobe implemented as a personal computer including both laptop computer andnon-laptop computer configurations.

Example embodiments may also include methods to restore a join featureto an online meeting invitation. These methods can be implemented in anynumber of ways, including the structures described herein. One such waymay be by machine operations, of devices of the type described in thepresent disclosure. Another optional way may be for one or more of theindividual operations of the methods to be performed in conjunction withone or more human operators performing some of the operations whileother operations may be performed by machines. These human operatorsneed not be collocated with each other, but each can be only with amachine that performs a portion of the program. In other embodiments,the human interaction can be automated such as by pre-selected criteriathat may be machine automated.

FIG. 7 illustrates a logic flow diagram for an example server-sideprocess to restore a join feature to an online meeting, arranged inaccordance with at least some embodiments described herein. Process 700may be implemented on a computing device, server, or other system. Anexample system may include a communication interface configured tofacilitate communication between a productivity service and anapplication of the productivity service, a memory configured to storeinstructions, and one or more processors coupled to the memory andconfigured to execute a communication module, wherein the communicationmodule is configured to restore a join feature to an online meeting.

Process 700 begins with operation 710, where a productivity service mayreceive an online meeting. The online meeting may be received from theapplication of the productivity service following generation of theonline meeting by a meeting organizer through the application.Alternatively, the online meeting may be received from a third partyservice, such as a calendar provider.

At operation 720, the productivity service may detect an absence ofmetadata associated with the join feature upon analysis of the onlinemeeting. The absent metadata may include information to generate and/orinsert a join feature, such as a join link, into the online meeting.

At operation 730, the productivity service may parse a body of theonline meeting to detect a collection of URLs by employing patternmatching. At operation 740, the productivity service may verify each ofthe URLs of the collection with a HTTP get operation to determinewhether any of the URLs have an online meeting identifier.

At operation 750, upon determination that a URL from the collectioncomprises an online meeting identifier, the productivity service mayrecreate the metadata with the URL to generate the join feature.Additionally, the productivity service may recreate the metadata withthe URL to generate the join feature in response to a determination thatmultiple URLs of the collection comprise a same online meetingidentifier. The join feature may be a join link and/or a join buttonconfigured to execute an operation to join the online meeting. Atoperation 760, the productivity service may then update the onlinemeeting with the metadata such that the join feature is able to berestored.

The operations included in process 700 are for illustration purposes.Restoration of a join feature to an online meeting may be implemented bysimilar processes with fewer or additional steps, as well as indifferent order of operations using the principles described herein. Theoperations described herein may be executed by one or more processorsoperated on one or more computing devices, one or more processor cores,specialized processing devices, and/or general purpose processors, amongother examples.

FIG. 8 illustrates a logic flow diagram for an example client-sideprocess to restore a join feature to an online meeting, arranged inaccordance with at least some embodiments described herein. Process 800may be implemented on a client device. An example client device mayinclude a communication interface configured to facilitate communicationbetween a productivity service and the client device, a memoryconfigured to store instructions, and one or more processors coupled tothe memory and configured to execute a communication module, wherein thecommunication module is configured to restore a join feature to anonline meeting. In some embodiments, the communication module may be anintegral component of an application associated with the productivityservice that is being executed on the client device.

Process 800 begins with operation 810, where the communication modulemay receive an online meeting. The online meeting may be newly generatedmeeting received from the productivity service or a third party service,such as a calendar provider. Alternatively, the online meeting may be anexisting meeting that has been edited by an organizer or invitees of theonline meeting.

At operation 820, the communication module may detect an absence ofmetadata associated with the join feature upon analysis of the onlinemeeting. The absent metadata may include information to generate and/orinsert a join feature, such as a join link, into the online meeting.

At operation 830, the communication may parse a body of the onlinemeeting to detect a collection of URLs by employing pattern matching. Atoperation 840, the productivity service may verify each of the URLs ofthe collection with a HTTP get operation to determine whether any of theURLs have an online meeting identifier.

At operation 850, upon determination that a URL from the collectioncomprises an online meeting identifier, the communication module mayrecreate the metadata with the URL to generate the join feature.Additionally, the communication module may recreate the metadata withthe URL to generate the join feature in response to a determination thatmultiple URLs of the collection comprise a same online meetingidentifier. The join feature may be a join link and/or a join buttonconfigured to execute an operation to join the online meeting.

The operations included in process 800 are for illustration purposes.Restoration of a join feature to an online meeting may be implemented bysimilar processes with fewer or additional steps, as well as indifferent order of operations using the principles described herein. Theoperations described herein may be executed by one or more processorsoperated on one or more computing devices, one or more processor cores,specialized processing devices, and/or general purpose processors, amongother examples.

According to some embodiments, means to restore a join feature to anonline meeting are provided. Example means may include receiving anonline meeting, detecting an absence of metadata associated with thejoin feature upon an analysis of the online meeting, parsing a body ofthe online meeting to detect a collection of URLs, verifying each URLfrom the collection with a hypertext transport protocol (HTTP) getoperation, and in response to a determination that a URL from thecollection comprises an online meeting identifier, recreating themetadata with the URL to generate the join feature.

According to some examples, methods to restore a join feature to anonline meeting are provided. An example method may include receiving anonline meeting, detecting an absence of metadata associated with thejoin feature upon an analysis of the online meeting, parsing a body ofthe online meeting to detect a collection of URLs, verifying each URLfrom the collection with a hypertext transport protocol (HTTP) getoperation, and in response to a determination that a URL from thecollection comprises an online meeting identifier, recreating themetadata with the URL to generate the join feature.

In other examples, the online meeting may be received from anapplication associated with the productivity service followinggeneration of the online meeting by an organizer through the applicationor the online meeting may be received from a third party service.Pattern matching may be employed to detect the collection within thebody of the online meeting. Recreation of the metadata with the URL togenerate the join feature may be foregone in response to a determinationthat no URL from the collection comprises an online meeting identifieror in response to a determination that more than one URL from thecollection of one or more URLs comprises an online meeting identifierand the respective online meeting identifiers are distinct.

In further examples, duplicate URLs may be removed from the collectionprior to verification. Verification of each URL from the collection withthe HTTP get operation may include determining whether each URLcomprises an online meeting identifier. The join feature may bedisplayed through an invitation to the online meeting. The metadataassociated with the join feature may include information to generate andinsert the join feature into the online meeting. The join feature may bea join link or a join button configured to execute an operation to jointhe online meeting.

According to some embodiments, client devices to restore a join featureto an online meeting may be described. An example client device mayinclude a communication interface configured to facilitate communicationbetween a productivity service and the client device, a memoryconfigured to store instructions, and one or more processors coupled tothe memory and configured to execute a communication module. Thecommunication module may be configured to receive an online meeting fromthe productivity service, detect an absence of metadata associated withthe join feature upon an analysis of the online meeting, parse a body ofthe online meeting to detect a collection of URLs, verify each URL fromthe collection with a HTTP get operation, and in response to adetermination that a URL from the collection comprises an online meetingidentifier, recreate the metadata with the URL to generate the joinfeature.

In other embodiments, the body of the online meeting may be formatted inhypertext markup language (HTML). The online meeting received may be anewly generated online meeting or may be an existing online meeting thathas been edited. The communication module may be an integral module ofone or more applications of the productivity service being executed bythe client device, where the applications may include a communicationapplication, a calendar application, a word-processing application, anotebook application, and a spreadsheet application.

According to some examples, methods to restore a join feature to anonline meeting may be provided. An example method may include receivingan online meeting, detecting an absence of metadata associated with thejoin feature upon an analysis of the online meeting, parsing a body ofthe online meeting to detect a collection of URLs by employing patternmatching, removing duplicate URLs from the collection, and verifyingeach remaining URL from the collection with a hypertext transportprotocol (HTTP) get operation. The example method may further include,in response to a determination that a URL from the collection of one ormore URLs comprises an online meeting identifier, recreating themetadata with the URL to generate the join feature, and displaying thejoin feature through an invitation to the online meeting.

In other examples, recreation of the metadata with the URL to generatethe join feature may be foregone in response to a determination that noURL from the collection comprises an online meeting identifier or inresponse to a determination that more than one URL from the collectioncomprises an online meeting identifier and the respective online meetingidentifiers are distinct. The online meeting is re-analyzed in responseto a determination that the online meeting is edited to determinewhether there is an absence of metadata associated with the joinfeature.

The above specification, examples and data provide a completedescription of the manufacture and use of the composition of theembodiments. Although the subject matter has been described in languagespecific to structural features and/or methodological acts, it is to beunderstood that the subject matter defined in the appended claims is notnecessarily limited to the specific features or acts described above.Rather, the specific features and acts described above are disclosed asexample forms of implementing the claims and embodiments.

What is claimed is:
 1. A method to restore a join feature to an onlinemeeting; the method comprising: receiving an online meeting; detectingan absence of a join Uniform Resource Locator (URL) of the onlinemeeting; parsing a body of the online meeting to detect a collection ofone or more URLs; verifying each URL from the collection of one or moreURLs with a hypertext transport protocol (HTTP) get operation; inresponse to a determination that a URL from the collection of one ormore URLs comprises an online meeting identifier of the online meeting:generating the join URL to include the online meeting identifier,wherein the join URL is configured to execute an operation to join theonline meeting, and displaying a user interface configured to access thejoin URL.
 2. The method of claim 1; wherein receiving the online meetingcomprises: receiving the online meeting from an application associatedwith a productivity service following generation of the online meetingby an organizer through the application.
 3. The method of claim 1,wherein receiving the online meeting comprises: receiving the onlinemeeting from a third party service.
 4. The method of claim 1, whereinparsing the body of the online meeting to detect the collection of theone or more URLs comprises: employing pattern matching to detect thecollection of one or more URLs within the body of the online meeting. 5.The method of claim 4, further comprising: in response to adetermination that no URL from the collection of one or more URLscomprises an online meeting identifier, foregoing-generation of the joinURL.
 6. The method of claim 4, further comprising: in response to adetermination that more than one URL from the collection of one or moreURLs comprises an online meeting identifier and the respective onlinemeeting identifiers are distinct, foregoing generation of the join URL.7. The method of claim 1, further comprising: removing duplicate URLsfrom the collection of one or more (URLs) prior to the verification ofeach URL.
 8. The method of claim 1, wherein verifying each URL from thecollection of one or more URLs with the HTTP get operation comprises:determining whether each URL comprises an online meeting identifier. 9.The method of claim 1, further comprising: displaying the join URLthrough an invitation to the online meeting.
 10. The method of claim 1,wherein a join button is configured to access the join URL to join theonline meeting.
 11. A client device to restore a join feature to anonline meeting, the client device comprising: a memory configured tostore instructions; and one or more hardware processors coupled to thememory and configured, by the instructions, to: receive an onlinemeeting; detect an absence of a join Uniform Resource Locator (URL) ofthe online meeting; parse a body of the online meeting to detect acollection of one or more uniform resource locators (URLs); verify eachURL from the collection of one or more URLs with a hypertext transportprotocol (HTTP) get operation; in response to a determination that a URLfrom the collection of one or more URLs comprises an online meetingidentifier of the online meeting: generate the join URL to include theonline meeting identifier, wherein the join URL is configured to executean operation to join the online meeting, and display a user interfaceconfigured to access the join URL.
 12. The client device of claim 11,wherein the body of the online meeting is formatted in hypertext markuplanguage (HTML).
 13. The client device of claim 11, wherein the onlinemeeting received is a newly generated online meeting.
 14. The clientdevice of claim 11, wherein the online meeting received is an existingonline meeting that has been edited.
 15. A method to restore a joinfeature to an online meeting, the method comprising: receiving an onlinemeeting; detecting an absence of a join Uniform Resource Locator (url)of the online meeting; parsing a body of the online meeting to detect acollection of one or more uniform resource locators (URLs) by employingpattern matching; removing duplicate URLs from the collection of one ormore URLs; verifying each remaining URL from the collection of one ormore URLs with a hypertext transport protocol (HTTP) get operation; inresponse to a determination that a URL from the collection of one ormore URLs comprises an online meeting identifier of the online meeting:generating the join URL to include the online meeting identifier,wherein the join URL is configured to execute an operation to join theonline meeting; and displaying a user interface configured to access thejoin URL.
 16. The method of claim 15, further comprising: in response toa determination that no URL from the collection of one or more URLscomprises an online meeting identifier or in response to a determinationthat more than one URL from the collection of one or more URLs comprisesan online meeting identifier and the respective online meetingidentifiers are distinct, foregoing generation of the join URL.
 17. Themethod of claim 15, further comprising: in response to a determinationthat the online meeting is edited, re-analyzing the online meeting todetermine whether there is an absence of a join URL within the onlinemeeting.